Skip to content

Conversation

@andygrove
Copy link
Member

@andygrove andygrove commented Nov 7, 2025

Which issue does this PR close?

Partial fix for #2649

Rationale for this change

In native code, we had a hard-coded UTC when converting Spark schema to Arrow schema.

In to_arrow_datatype:

DataTypeId::Timestamp => {
          ArrowDataType::Timestamp(TimeUnit::Microsecond, Some("UTC".to_string().into()))
      }

This would lead to a runtime error when running a query against a DataFrame (not a Parquet file) that is not in UTC:

RowConverter column schema mismatch, expected Timestamp(Microsecond, Some("America/Denver")) got Timestamp(Microsecond, Some("UTC")).

What changes are included in this PR?

Pass Spark timeZoneId into native code and use that instead of hard-coded UTC.

How are these changes tested?

WIP

@codecov-commenter
Copy link

codecov-commenter commented Nov 7, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.23%. Comparing base (f09f8af) to head (c950217).
⚠️ Report is 675 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #2734      +/-   ##
============================================
+ Coverage     56.12%   57.23%   +1.10%     
- Complexity      976     1371     +395     
============================================
  Files           119      147      +28     
  Lines         11743    13843    +2100     
  Branches       2251     2376     +125     
============================================
+ Hits           6591     7923    +1332     
- Misses         4012     4692     +680     
- Partials       1140     1228      +88     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@andygrove
Copy link
Member Author

@parthchandra @mbutrovich I'm not looking for a review yet, but I'd like to discuss this with you both next week. I understand the issue much better now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants